Azure DevOps with SAFe
We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from …
Starting at $2 per GB (first 2GB free)
View PricingOverview
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Azure Artifacts
$2
Cloud
per GB (first 2GB free)
Basic Plan
$6
Cloud
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
Cloud
per extra parallel job (1 free parallel job with unlimited minutes)
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Demos
Azure Pipeline Tutorial | Azure Pipeline Deployment | Azure DevOps Tutorial | Edureka Rewind - 3
YouTube
Product Details
- About
- Tech Details
- FAQs
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities, along with the basic plan which includes:
- Azure Pipelines: automatically builds and tests code, combines continuous integration (CI) and continuous delivery (CD)
- Azure Boards: Work item tracking and Kanban boards
- Azure Repos: Unlimited private Git repos
- Azure Artifacts: 2 GB free per organization
Azure DevOps Services Video
Introduction to Azure DevOps
Azure DevOps Services Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
Reviewers rate Support Rating highest, with a score of 8.1.
The most common users of Azure DevOps Services are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(451)Attribute Ratings
Reviews
(1-25 of 30)Companies can't remove reviews or game the system. Here's why
January 09, 2024
Azure DevOps with SAFe
Score 10 out of 10
Vetted Review
Verified User
We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from Work items, Dashboards, Repo, CI/CD pipelines etc..
- Product Management
- Delivery Plans
- CI/CD
- Integrate GitHub with Azure DevOps and have just one product
- Automatic set Start and Target Date for Delivery Plan based on user story sprint assignment
August 03, 2023
Agile application for best project management practices
The application has provided the most suitable agile tools for managing projects in the organization. It tracks closely the task development infrastructure to enhance best implementation practices. My team has been depending on this platform for the last one year and the results have come out with positive ROI. Azure DevOps Services helps each department in performance modelling.
- Monitoring web development process.
- Building workflow pipeline.
- Customization of dashboards.
- Our goals have been implemented positively.
- I have not experienced any missing feature.
June 06, 2023
ADO - an all encompassing tool.
Score 8 out of 10
Vetted Review
Verified User
We use ADO for a wide range of things. We create work items in there, essentially being a unique number that we can associate with a project. We also use ADO to create features, user stories, acceptance criteria, and test cases in ADO. The linking system in ADO allows good visibility across these.
- The use of the scrum-like board, which can be customized to your liking.
- Excellent linking and visibility across items in ADO e.g. user stories, features, test cases, tasks, etc.
- Storing Test Cases.
- I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
- The wiki is not the prettiest thing to look at, so it could have refinements there.
- It could improve the search slightly better.
Score 8 out of 10
Vetted Review
Verified User
I use Azure DevOps to schedule runs for automated test cases. It provides the feature to share results via Webhooks. So the team is able to know about the status of the test runs by alerts configured via Webhooks.It helps to track builds and perform dependency checks. It helps to create builds and deploy them.
- Dependency check for builds
- Deploy the builds in the respective environments
- Run the tests in different stages within Azure DevOps
- When I cancel a release, it asks for adding comments however, finding that comment later is difficult, the automated emails shared for each build do not contain the comments as well.
- The UI/UX can be improved to be more intuitive
Azure DevOps Services are used to manage our daily work tasks. This helps us to keep track of the progress of each task accordingly, with this we can check the status of each task from one stage to another, we can assign the task to the correct personnel within the organization, and leave comments/attachments inside as well.
- Keep track of working tasks across organization.
- Set up automated CI/CD pipelines.
- Overview/detailed view of overall working progress.
- UI can be more user-friendly.
- Navigation between tasks can be smoother.
- Warning before leaving the page when there's a draft can be useful.
As an IT Service Manager, I use Azure DevOps Services to improve on our existing software development and IT service management processes. We mostly use the built-in source control, work tracking, build automation, and release management functions of Azure DevOps. Our use case involves several software development projects and focuses mainly on Source Control and Collaboration to allow our dev teams to securely store and collaborate on their code, Work item tracking to track the progress of bug fixes and enhancements, as well as user stories, Build Automation to reduce errors and speed up the dev cycle Automating deployments using the built-in release management functions.
- Tracking of user stories, bugs, and dev tasks, which allows our devs and business analysts to collaborate.
- Automated and better-controlled software deployments.
- DevOps has improved how our devs handle version control of their code (fewer conflicts).
- The sheer number of features can be overwhelming for new users!
- Better integration with external tools such as our service management platform.
- Setting up build configs and pipelines can be tricky for first-timers.
We deliver all the CI/CD processes of a mortgage company marketing department located in the US to the Azure portal. Web UI services, APIs, Function Apps, etc.
- Visual orchestration of CI/CD process.
- Track of current/last satisfactory delivered to environments.
- Open to connecting to different Azure/AWS services to deliver software.
- Improvement in metrics and dependencies.
- Improve the pricing for more than one build agent at a time.
- Connection to Power BI.
March 31, 2023
Your Code, Project and Team, safe in one place
Azure DevOps offers a wide variety of tools for a CI/CD environment and it's really useful. We are moving from a static build model to an automated one and so VSTS has the tools we need to continue growing in the future. We started using VSTS, now Azure DevOps, as a code repository only and that's the main use within our organization.
- Private repositories
- User management
- Security
- Extensions
- Some integration with 3rd party tools or services could be better
- Has a lot of options, but sometimes are hard to find
- Non standard build/test workflows could be problematic
December 29, 2021
Pure-Smarter Planning and Collaborative Product
Score 9 out of 10
Vetted Review
Verified User
In my opinion, This is one of the Hottest products right now booming in the market. This has solved lot of problems in terms of Automation and End to End Deployments. In our organization, We are using this for
1. To track Team's Efforts in terms of User stories and Assigning Tasks.
2. Storing all the code and performing End to End Deployment and Testing from Development phase to Production Phase.
This has actually solved a lot of problems which all the Team members used to face few years back, setting the tasks, scope, completion is now smoother and easier for everyone.
We also have the option to Integrate with other software's and perform the deployments which is a huge plus.
1. To track Team's Efforts in terms of User stories and Assigning Tasks.
2. Storing all the code and performing End to End Deployment and Testing from Development phase to Production Phase.
This has actually solved a lot of problems which all the Team members used to face few years back, setting the tasks, scope, completion is now smoother and easier for everyone.
We also have the option to Integrate with other software's and perform the deployments which is a huge plus.
- Azure Boards to Assign tasks, User stories to team members and track their time so easily.
- Azure Repos used to store all the code used from Development phase to Production Phase.
- Azure Pipelines - Great feature to deploy the products with End to End testing.
- Automating any kind of solution/problem on Azure Cloud using PowerShell/CLI scripting.
- Security of the Third Party Plugins Integrated with the Pipelines.
- Notification of the Tasks which are getting closer in time.
- Can Improve in terms of integrating few more required software.
November 07, 2021
Project starts with Microsoft Tools
Azure DevOps is used for project management of our sprint tickets to assign within team and provide the dashboard information to our project managers. The user story is easy to create and assign to the owner and then create the sub-task to assign within the user for different tasks like (Development, Peer QA, Final QA e.t.c)
- User Story
- Dashboard
- Sub Task Creation
- Reporting
- Divide sub task and timings
- Time divide between each task
- Integration with other tools is difficult
August 20, 2021
Best Agile/DevOps management platform
We use Azure DevOps Services as our main DevOps platform for our IT projects.
The product usage changes from a project to another.
The most used capability is the agile planning tool, for Dev and non dev IT projects management.
We also use the GIT code versioning tools, along with DevOps build/deployment pipelines, in Microsoft technologies based Dev projects.
We are now planning trainings so that we can use the testing tools properly as well
The product usage changes from a project to another.
The most used capability is the agile planning tool, for Dev and non dev IT projects management.
We also use the GIT code versioning tools, along with DevOps build/deployment pipelines, in Microsoft technologies based Dev projects.
We are now planning trainings so that we can use the testing tools properly as well
- makes Agile collaboration easy
- DevOps made "easy" (after a learning time)
- very clear and intuitive UI
- very large set of connectors/integrations/extensions
- Office 365 integration (Teams and Sharepoint)
- plenty of training/documentation resources, and large community of users
- the online documentation on Microsoft Developer Network should be clearer and easier to read, even for senior users
- advanced configuration is hard to understand
- product features changes can sometimes surprise you
April 15, 2021
Azure DevOps: ADO your CI-CD
Azure DevOps or ADO (as we call it) is used by the IT department in developing and also transforming multiple legacy applications to Modern Microservices based applications and architecture. It enables seamless development by offering multiple tools that are required to develop modern applications in Agile-based methodologies. It enables seamless Continuous Integration, Continuous Deployment (CI/CD) process, and everything is bundled in a user-friendly manner.
- Azure DevOps bundles all the useful tools together in a seamless way.
- Sprint boards, Code repositories, Pipelines etc. all can be managed from a single application.
- Facilitates easy collaboration between technical members and business or product owners.
- Facilitates parity between different environments by providing a single source of truth for all pipelines.
- Azure DevOps Sprint boards can be improved, similar to Jira (this can be my bias).
- Teams and Azure DevOps integration can be improved in-terms of updates of stories or tasks.
- Pipeline job logs and their web console views can be improved.
September 13, 2020
Full agile development workflow in one complete package
We use Azure DevOps/VSTS for the entire agile approach to software development at the organization I work for. We use Azure Boards for managing work in sprints, providing us with live features for planning & retrospectives. We use the Azure Repos feature for Git version control of our code and for PR processes, and pipelines & releases for building, linting, and testing code & deploying code to multiple environments via a continuous integration approach. We use Azure Artifacts to host our NuGet packages to be used by multiple projects for code reusability.
- Git repositories feature is fully featured with a friendly web interface.
- Azure pipelines & releases are very flexible for CI/CD practices.
- Azure Boards allows linking work items to code and for a closer relationship between code & the sprint rather than using a secondary piece of software like JIRA/Trello.
- User interface looks nice but it can often be quite hard to find things that you need.
- Documentation can be limited.
February 15, 2020
Azure DevOps Eases the Pain
We are using Azure DevOps across most teams, leveraging both Kanban and Scrum methodologies. The tool is used for SDLC workflow, source control, and documentation.
- Source control integration.
- Templates for multiple Agile types.
- Document management (implement something similar to Sharepoint libraries).
- Streamlined permissions structure.
Azure DevOps is being used by our development department. It addresses the problem of not having a central source code storage location with team collaboration. It is used to store and collaborate on development projects. All team members are checking in/out their source code and pipelines/team collaboration is in use.
- Ease of use/integration with Visual Studio.
- Very responsive and easy to maintain a site.
- Has full Git capabilities.
- Capability to store unlimited numbers of projects.
- The price/license per user could be a little less than many of the open-source type source code platforms on the market.
- Ease of integration with other development IDE's than Visual Studio.
October 10, 2019
Get Quick Pipelines Up and Running with Azure DevOps
Azure DevOps is a common tool used by technical teams. In my capacity I used Azure DevOps to create a Chef Cookbook pipeline for delivering tested code. In doing this, I used it in conjunction with the built in version control system provided by Azure DevOps, but it also integrates well with GitHub and other systems.I also helped others set up pipelines and implement the use of Azure DevOps in this capacity as well.
- Usability: The usability of Azure DevOps is great! Being a new user, it was easy to pick up and go with this tool with very little requirement to seek external documentation.
- Integration: This tool integrates well with other systems (ie. GitHub, Chef, etc).
- Built in activities: Azure DevOps has a ton of prebuilt activities that allow you to basically build whatever you need without writing any extensive code.
- While usability is great, it did take me a few times to find "hidden areas" (like the visual designer link for creating pipelines). Having these in more defined noticeable areas will only improve on the already great usability.
- As with other Microsoft tools, the Microsoft login get's a little crazy when you have multiple accounts. In my case, I have several accounts (personal, university, and work) and getting into Azure DevOps with the appropriate account could sometimes be an act of futility.
August 19, 2019
Azure DevOps for large Enterprise
Azure DevOps is currently used across the organization. Currently not all groups and departments are utilizing it however we are in the process of rolling out to these groups. Azure DevOps has become our go to application for development. We are using it for full development life cycle, code repository, testing, deployment and verification.
- Once set up it makes deployments to various environments a breeze
- YAML backend is a huge plus
- Large groups can work on the same solution seamlessly
- More streamlined set up of CI/CD
- Better error messaging to explain why sometimes a build is successful and sometimes not
- Easier set up of deployment tools
August 12, 2019
Great tool for DevOps methodology that can contribute with your projects and team performance
We use Azure DevOps to manage all our projects across the whole organization. The project manager usually translates all software requirements to Azure DevOps and assign appropriate tasks to programmers. It is a very flexible tool to implement DevOps methodology. The project development is followed through the platform, as well as the team performance.
- Easy representation of software requirements in user stories and tasks.
- It allows the tracking of activities and team performance
- It allows interaction between team members in a specific task
- You can use only a few tools to complement your existent workflow
- There is a free version for small teams (up to 5 users)
- Some small improvements could be done in the user interface.
- Sometimes the performance is low (some requests/queries are slow)
May 16, 2019
A fully featured DevOps suite
We're implementing entire product workflows with Azure DevOps: building, testing, staging and deploying. It's the perfect companion for Visual Studio and Git, so everyone just loves using it. It's a dream come true not having to switch to different front-ends to get our job done throughout the day, while keeping an amazing user experience.
- Unified environment for all DevOps tasks and procedures
- Amazing User Experience within a beautiful UI
- Great marketplace extensions collection
- Code merging has room for improvement
- Such a broad set of features can become confusing for the novice user
Azure DevOps is the standard at my company for software source code management and project/requirements management. The cloud-hosted software is being used across all teams to coordinate and track development activities, align release planning, and track work items for testing and verification. Previously we used tools such as Rally and Perforce to serve these needs, but we have standardized on Azure DevOps going forward.
- Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
- Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
- Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
- Central Dashboard of Development Metrics: AZDO nests its dashboards in workflow-specific tracks, which is useful. Still, I'd like to see a home page personalized for each user which provides relevant updates on the most recent work items (updates to features, etc.) and work progress.
- Complex Queries: AZDO is great for simple queries, but complex queries and the display of results doesn't always produce intuitive results. For example, sorting and drag/drop can be unreliable in some views. I suspect the AZDO team will work out these issues over the next few releases.
- Lack of Themes: AZDO allows for the tracking of Epics and Initiatives, but there doesn't seem to be a structured interface for tracking product investment themes.
November 12, 2018
VSTS is a great tool - but just for development teams
It is being used and maintained by our engineering team for development work. Product management accesses VSTS to see project statuses and write user stories.
- Writing detailed use stories
- Assigning people to tasks
- Allowing for attachments
- It has nice tools for gathering data for reporting purposes.
- Having a more modern user interface which doesn't feel outdated.
- VSTS is very development team-centric. Development teams are working very closely with product management, who sets their tasks and priorities. There is no way in VSTS for product managers to develop product roadmaps based on product strategies and trickle that down to user stories for developers. The link between product management and development is missing.
- Tools like Estimably or something similar for pointing stories in an agile development setting would be very useful, as they are used daily by agile teams.
- More built-in visual reporting functionality that could be customized would be a huge asset.
June 06, 2018
VSTS the best for Microsoft builds
VSTS is currently being used by one department at work but was I brought it into the company about six years ago. We currently use VSTS as a building and testing tool. We set up the builds and create tests to run after a build is successful. When I first started with VSTS I set it up to run on a daily basis and then had the developers correct the problems that were shown by the tests. This works very well and the developers like using it since they did not have to keep on integrating their changes together.
- VSTS has a wonderful integration with Team Foundation Source control and Git. This is good because these were two source control systems that we used.
- VSTS can be scheduled to run its builds and test at various times of the day. This means it can in the middle of the night and be ready for the developers when they get in in the morning.
- VSTS handles Microsoft builds very easily. Building a .Net application can be set up with almost no work. You just have to use the Visual Studio solution that was used by the developers to create the application.
- VSTS is very Microsoft centric. If the application you want to build is not based on Microsoft items such as C#, or Visual Basic it is very difficult to use.
- If you are using the latest version of VSTS then you will find a documentation problem. It can be very hard to find methods and help trying to get something running.
- Passing data between VSTS build steps is not easy. It can be done, but it is not a normal thing that you would Microsoft would have put into their product.
June 05, 2018
VSTS will save you time/money
Microsoft Visual Studio Team System (VSTS) is being used currently only by IT and a few select people in the business unit. The main goal of using VSTS from the business perspective was to improve communication, work item management, improve planning and increase visibility into product management. For the developers in IT, it was imperative to have more integration between business requirement and code, moreover, it also expedited development workflow (code reviews, etc).
- Work item management is fantastic and easy to use. It can be used as simply just tracking tasks, or as complex as tracing work items from multiple projects being assigned to a single developer. Work items can be customized easily to meet the needs of your organization as well, and it isn't difficult to manage the customization.
- Source code management is excellent and tied directly into VSTS. You have a choice of TFVC or GIT management options - we've switched to git and have not looked back. It is fully featured and commits can be tied directly to a work item using # tags.
- Metrics/dashboard - being able to write simple queries and move them to a dashboard in a few minutes is great. It enables team managers a quick board to review the status of a project and quickly act on any issues cropping up.
- Build and release management - if you don't have this... you'll want it. The integration is magic, the interface is easy, and to setup an automated build using the hosted agent was a breeze. We did have to purchase an additional license because of the number of builds we had, but it was worth it.
- VSTS has a log of flexibility... almost too much. It's hard to actually decide how best to use it until you just set it up and try it out.
- Currently getting a list of work items on the main home page is messy. There's no hierarchy so it can sometimes be just a blast of work without any sorting or prioritization settings. There's a simple work-around to simply create a query for yourself and enable "search across multiple projects". That works alright, but it would be a better experience if the home page had this already covered.
- Teams management could be better. It's a little confusing, and not easy to setup. Our specific use case of having some teams able to only see their backlog and nothing else was not achievable in the current implementation of VSTS. As a result, whenever we have to contract out work, we end up creating a new Team Project. It's not all bad, because team project contents can be easily migrated to another project, but it's still a bit annoying.
April 12, 2018
VSTS makes building and releasing applications a breeze
The team I work on uses Microsoft Visual Studio Team (VSTS) for code storage and versioning, as well as utilizing their build and release systems. This resolves multiple issues including removing the need for us to manage a local repository and helps automate the process of building and releasing new versions of our application by leveraging automatic processes triggered when branch is pushed to the remote server.
- Code repository
- Automatic Build & Release
- User management
April 10, 2018
Visual Studio Team Services Review
Visual Studio Team Services (VSTS) is being used by our client's organization, therefore, we didn't pick it ourselves. It is used by our project manager to manage the project and the various features we are developing. With VSTS, it is easy to implement the software development lifecycle using agile principles. Our client is huge on agile and VSTS is a good solution for that method of project management.
- It's easy to see the work that you are assigned. VSTS also encourages the use of its additional details so features don't get confusing
- You can track progress of a particular sprint so you can see how far ahead or behind you are during a certain sprint
- Integration with git is excellent so viewing difference in files, previous commits, etc. are easy with VSTS
- The Query functionality is hard to use. I understand that its supposed to let users get more control of what they want to see, but its not easy
- It's hard to see total hours spent on a project. I mentioned in the pro that you can track progress, but it's hard to track how much effort was already spent
- Build scripts can be confusing to use. Sometimes builds fail for random reasons, but to re-run a build can be confusing